Reducing power for 3d workloads

ABSTRACT

Various embodiments are presented herein that may reduce the workload of a GPU tasked with delivering frames of video data to a display generated by a  3 D application executing within a system or computing platform.  3 D applications executing within the system may generate new frames of video content at a specified frame rate known as frames per second (FPS). These frames are then delivered to a display communicatively coupled with the system for rendering. Every display has a refresh rate specified in cycles per second or Hertz (Hz). Vertical Synchronization (VSYNC) is a setting that synchronizes the frames per second (FPS) of a given application with the display&#39;s refresh rate. Forcing VSYNC on the application while the system is operating on battery power may reduce the workload on the GPU when the FPS is greater than the refresh rate resulting in greater battery life.

BACKGROUND

Computing platforms are generally capable of operating on a direct power source or on battery power when a direct power source is unavailable. Battery power is naturally a finite resource and must be recharged periodically. Considerable thought has gone into methods and techniques for extending the operating time of a computing platform while operating on battery power. Many computing platforms utilize both central processing units (CPUs) and graphics processing units (GPUs) within an overall system. One technique for reducing overall system power consumption and extending battery life is to reduce the frequencies at which the CPU and GPU operate while on battery power. This technique does not necessarily reduce the amount of work performed by the CPU or GPU—rather it slows down the pace at which the work is done. Another approach may be to reduce the actual workload associated with an application executing on either the CPU or GPU. Accordingly, there may be a need for improved techniques to solve these and other problems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an architecture suitable for carrying out embodiments of the invention.

FIG. 2 illustrates another block diagram of an architecture suitable for carrying out embodiments of the invention.

FIG. 3 illustrates one embodiment of a logic flow.

FIG. 4 illustrates one embodiment of a logic flow.

FIG. 5 illustrates one embodiment of a logic flow.

FIG. 6 illustrates an embodiment of a system that may be suitable for implementing embodiments of the disclosure.

FIG. 7 illustrates embodiments of a small form factor device in which the system of FIG. 6 may be embodied.

DETAILED DESCRIPTION

Various embodiments are presented herein that may reduce the workload of a GPU tasked with delivering frames of video data to a display generated by a three dimensional (3D) application executing within a system or computing platform. 3D applications executing within the system may generate new frames of video content at a specified frame rate known as frames per second (FPS). The GPU may be responsible for actually generating the frames. These frames are then delivered to a display communicatively coupled with the system for rendering. Every display has a refresh rate specified in cycles per second or Hertz (Hz). The refresh rate refers to the number of times the display can render a frame each second. A 60 Hz refresh rate means that the display can render 60 FPS.

VSYNC stands for Vertical Synchronization. VSYNC is a setting that synchronizes the frames per second (FPS) of a given application with the display's refresh rate. When VSYNC is disabled, the frames per second (FPS) utilized by a given application and refresh rate of the display have no relationship to each other as such. This lets the GPU work as fast as it wants, sending frames to the display as fast as it can draw them. Whether the display can actually show all these frames properly or not is another matter. For example, a 60 Hz display that is receiving video from an application operating at 120 FPS may display only 60 frames at most during any given second. The other 60 frames the GPU is producing are not being displayed and are wasted. Forcing VSYNC on the application while the system is operating on battery power may reduce the workload on the GPU. The GPU may not be required to generate as many frames as the application specifies if the refresh rate of the display cannot handle the FPS setting of the application.

Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claimed subject matter.

FIG. 1 illustrates a system 100 implementing an exemplary computing platform. The system 100 may include a processor circuit denoted as CPU 110, a second processor circuit denoted as GPU 125, and memory 112. One or more 3D applications 105 may be executing under the control and supervision of the CPU 110. The system 100 may further include a graphics driver 120 operative on CPU 110. There may be an instance of the graphics driver 120 associated with each 3D application 105. Each 3D application 105 may create a 3D context (e.g., a GPU state). The graphics driver 120 may be operative to enable a VSYNC setting to control the FPS that the GPU generates for a given 3D application. The GPU 125 may also include a VSYNC controller component 130 operative to enforce the VSYNC setting to synchronize the FPS of a 3D application to the refresh rate of a display 160.

The system 100 may be powered by either an external direct current (DC) source 150 or a battery 140. The graphics driver 120 may be operative to determine whether the system 100 is being powered by the external DC source 150 or the battery 140. The system 100 may also be communicatively coupled with the display 160. The display 160 may be associated with one or more refresh rates that control how often the display 160 refreshes its screen with a new frame. The display 160 may receive frames from the GPU 125 at a frame rate specified by the 3D application. A 3D application 105 may provide for one or more different frame rates during execution and may also include a setting for VSYNC in which the frame rate will be synced to the refresh rate of the display 160.

The system 100 of FIG. 1 has been illustrated as integrated into a single platform. For instance, the CPU 110 and GPU 125 may be on the same processor die. Another embodiment is illustrated in FIG. 2 in which the CPU 110 and the GPU 125 are not necessarily on the same processor die. The GPU 125 may be, for instance, a separate graphics processing card communicatively coupled with the CPU 110.

The system 200 of FIG. 2 generally operates similar to the system 100 of FIG. 1. One or more 3D applications 105 may be executing under the control of the CPU 110 and memory 112. The graphics driver 120 may include separate instances for each of the 3D applications 105. Each 3D application 105 may create a 3D context (e.g., a GPU state). The graphics driver 120 may be operative to enable a VSYNC setting to control the FPS that the GPU generates for a given 3D application. The GPU 125 may also include a VSYNC controller component 130 operative to enforce the VSYNC setting to synchronize the FPS of a 3D application to the refresh rate of a display 160.

The system 200 may be powered by either an external DC source 150 or a battery 140. The graphics driver 120 may be operative to determine whether the system 200 is being powered by the external DC source 150 or the battery 140. The system 200 may also be communicatively coupled with the display 160. The display 160 may be associated with one or more refresh rates that control how often the display 160 refreshes its screen with a new frame. The display 160 may receive frames from the GPU 125 at a frame rate specified by the 3D application. A 3D application 105 may provide for one or more different frame rates during execution and may also include a setting for VSYNC in which the frame rate will be synced to the refresh rate of the display 160.

Included herein are one or more flow charts representative of exemplary methodologies for performing novel aspects of the disclosed architecture. While, for purposes of simplicity of explanation, the one or more methodologies shown herein, for example, in the form of a flow chart or flow diagram, are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation.

FIG. 3 illustrates one embodiment of a logic flow 500 in which battery power is conserved by reducing the workload of the GPU 125 according to embodiments of the invention. The logic flow 300 may be representative of some or all of the operations executed by one or more embodiments described herein.

The illustrated embodiment shown in FIG. 3 may reduce the workload of a GPU tasked with delivering frames of video data to a display generated by a 3D application executing within a system or computing platform. 3D applications executing within the system may generate new frames of video content at a specified frame rate or FPS. The system 100 may include a CPU 110 and a GPU 125. One or more 3D applications 105 may be executing under the control and supervision of the CPU 110. The system 100 may further include a graphics driver 120 operative on CPU 110. There may be an instance of the graphics driver 120 associated with each 3D application 105. Each 3D application 105 may create a 3D context (e.g., a GPU state). The graphics driver 120 may be operative to determine when the system 100 is operating on battery power 140. The graphics driver 120 may be operative to enable a VSYNC setting to control the FPS that the GPU generates for a given 3D application. When the system 100 is operating on battery power 140, the graphics driver 120 may force VSYNC on the 3D application 105. A 3D application 105 may provide for one or more different frame rates during execution and may also include a setting for VSYNC in which the frame rate will be synced to the refresh rate of the display 160. The GPU 125 may also include a VSYNC controller component 130 operative to enforce the VSYNC setting to synchronize the FPS of a 3D application 105 to the refresh rate of a display 160. The system 100 may also be communicatively coupled with the display 160.

In the illustrated embodiment shown in FIG. 3, the CPU 110 may be executing a 3D application 105 at block 310. For example, one or more 3D applications 105 may be executing on the system 100 under the control of CPU 110. Each 3D application 105 may be associated with an instance of the graphics driver 120. Under normal operating conditions, the 3D application(s) will execute according to the settings specified within the given 3D application 105. The embodiments are not limited in this context.

The logic flow 300 may determine whether the system 100 is operating on battery power 140 at block 320. For example, the system 100 may be operative on battery power 140 or may receive power from an external DC source 150. An external DC source 150 may be representative of the system being plugged in to an alternating current (AC) outlet. The power from the AC outlet may pass through a rectifier that converts it to DC for operating the system 100. When the system 100 is receiving power from an external DC source 150, power consumption is less of an issue. However, when the system 100 is receiving power from a battery 140, power consumption is an issue because the charge in the battery 140 is limited and dwindles with system 100 use. The graphics driver 120 may be capable of determining when the system 100 is operating on battery power 140. In such cases, certain power savings techniques may be implemented to extend the life of the battery while powering the system 100. The embodiments are not limited in this context.

The logic flow 300 may force execution of the VSYNC setting when the system 100 is operating on battery power 140 at block 330. For example, an instance of the graphics driver 120 may be associated with a 3D application 105. The graphics driver 120 may have determined that the system 100 is operating on battery power 140. In an effort to conserve power while operating on battery power 140, the graphics driver 120 may enable or force VSYNC between the 3D application 105 and the display 160. The graphics driver 120 signals the GPU 125 to lower the frame rate to match the refresh rate of the display 160. The embodiments are not limited in this context.

The GPU 125 may present frames to the display 160 at block 340. For example, the GPU 125 generates frames of video content for the display 160. If the system 100 is operating on battery power 140, the GPU 125 may present the frames to the display 160 under VSYNC. The FPS for the 3D application 105 will be forced into VSYNC to match the refresh rate of the display 160. Consider a 3D application 105 operating with a frame rate of 90 FPS. The display 160 may have a refresh rate of 75 Hz. In this example, VSYNC will cap the GPU 125 workload at 75 FPS rather than 90. Since the GPU 125 does not have to generate the additional 15 frames its workload has been reduced thereby conserving power. The embodiments are not limited in this context.

The GPU 125 may present frames to the display 160 at block 350. For example, the GPU 125 generates frames of video content for the display 160. If the system 100 is operating on power form an external DC source 150 that is not the battery 140, the GPU 125 may present the frames to the display 160 as intended by the 3D application 105. The embodiments are not limited in this context.

FIG. 4 illustrates another embodiment of a logic flow 400 in which battery power is conserved by reducing the workload of the GPU 125 according to embodiments of the invention. The logic flow 400 may be representative of some or all of the operations executed by one or more embodiments described herein.

The illustrated embodiment shown in FIG. 4 may reduce the workload of a GPU tasked with delivering frames of video data to a display generated by a 3D application executing within a system or computing platform. 3D applications executing within the system may generate new frames of video content at a specified frame rate or FPS. The system 100 may include a CPU 110 and a GPU 125. One or more 3D applications 105 may be executing under the control and supervision of the CPU 110. The system 100 may further include a graphics driver 120 operative on CPU 110. There may be an instance of the graphics driver 120 associated with each 3D application 105. Each 3D application 105 may create a 3D context (e.g., a GPU state). The graphics driver 120 may be operative to determine when the system 100 is operating on battery power 140 and how much of the battery power remains. The graphics driver 120 may be operative to enable a VSYNC setting to control the FPS that the GPU generates for a given 3D application when the battery power remaining falls below a threshold level. When the system 100 is operating on battery power 140, the graphics driver 120 may force VSYNC on the 3D application 105. A 3D application 105 may provide for one or more different frame rates during execution and may also include a setting for VSYNC in which the frame rate will be synced to the refresh rate of the display 160. The GPU 125 may also include a VSYNC controller component 130 operative to enforce the VSYNC setting to synchronize the FPS of a 3D application to the refresh rate of a display 160. The system 100 may also be communicatively coupled with the display 160.

In the illustrated embodiment shown in FIG. 4, the CPU 110 may be executing a 3D application 105 at block 410. For example, one or more 3D applications 105 may be executing on the system 100 under the control of CPU 110. Each 3D application 105 may be associated with an instance of the graphics driver 120. Under normal operating conditions, the 3D application(s) will execute according to the settings specified within the given 3D application 105. The embodiments are not limited in this context.

The logic flow 400 may determine whether the system 100 is operating on battery power 140 at block 420. For example, the system 100 may be operative on battery power 140 or may receive power from an external DC source 150. An external DC source 150 may be representative of the system being plugged in to an alternating current (AC) outlet. The power from the AC outlet may pass through a rectifier that converts it to DC for operating the system 100. When the system 100 is receiving power from an external DC source 150, power consumption is less of an issue. However, when the system 100 is receiving power from a battery 140, power consumption is an issue because the charge in the battery 140 is limited and dwindles with system 100 use. The graphics driver 120 may be capable of determining when the system 100 is operating on battery power 140. In such cases, certain power savings techniques may be implemented to extend the life of the battery while powering the system 100. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 4, the logic flow 400 may determine a percentage level of remaining battery power 140 at block 430. For example, the graphics driver 120 may be operative to determine how much battery power 140 remains at a given time. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 4, the logic flow 400 may determine whether the percentage level of remaining battery power 140 has dipped below a threshold at block 440. For example, the graphics driver 120 may be operative to determine how much battery power 140 remains at a given time and compare it to a threshold level. The system may be set to invoke power savings once the battery dips below a pre-defined threshold level rather than automatically conserve power upon detection of battery power 140. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 4, the graphics driver 120 may force execution of the VSYNC setting when the system 100 is operating on battery power 140 below a threshold level at block 450. For example, an instance of the graphics driver 120 may be associated with a 3D application 105. The graphics driver 120 may have determined that the system 100 is operating on battery power 140 and that the battery power has dipped below a pre-defined threshold level. In an effort to conserve power while operating on battery power 140, the graphics driver 120 instance for a given 3D application 105 may then enable or force VSYNC between the 3D application 105 and the display 160. The graphics driver 120 signals the GPU 125 to lower the frame rate to match the refresh rate of the display 160. The embodiments are not limited in this context.

The GPU 125 may present frames to the display 160 at block 460. For example, the GPU 125 generates frames of video content for the display 160. If the system 100 is operating on battery power 140 below a threshold level, the GPU 125 may present the frames to the display 160 under VSYNC. The FPS for the 3D application 105 will be forced into VSYNC to match the refresh rate of the display 160. Consider a 3D application 105 operating with a frame rate of 90 FPS. The display 160 may have a refresh rate of 75 Hz. In this example, VSYNC will cap the GPU 125 workload at 75 FPS rather than 90. Since the GPU 125 does not have to generate the additional 15 frames its workload has been reduced thereby conserving power. The embodiments are not limited in this context.

The GPU 125 may present frames to the display 160 at block 470. For example, the GPU 125 generates frames of video content for the display 160. If the system 100 is operating on power form a external DC source 150 that is not the battery 140 or if the system 100 is operating on battery power 140 but above a threshold level, the GPU 125 may present the frames to the display 160 as intended by the 3D application 105. The embodiments are not limited in this context.

FIG. 5 illustrates one embodiment of a logic flow 500 in which battery power is conserved by reducing the workload of the GPU 125 according to embodiments of the invention. The logic flow 500 may be representative of some or all of the operations executed by one or more embodiments described herein.

The illustrated embodiment shown in FIG. 5 may reduce the workload of a GPU tasked with delivering frames of video data to a display generated by a 3D application executing within a system or computing platform. 3D applications executing within the system may generate new frames of video content at a specified frame rate or FPS. The system 100 may include a CPU 110 and a GPU 125. One or more 3D applications 105 may be executing under the control and supervision of the CPU 110. The system 100 may further include a graphics driver 120 operative on CPU 110. There may be an instance of the graphics driver 120 associated with each 3D application 105. Each 3D application 105 may create a 3D context (e.g., a GPU state). The graphics driver 120 may be operative to determine when the system 100 is operating on battery power 140 and how much of the battery power remains. The graphics driver 120 may be operative to enable a VSYNC setting to control the FPS that the GPU generates for a given 3D application when the battery power remaining falls below a threshold level. When the system 100 is operating on battery power 140, the graphics driver 120 may force VSYNC on the 3D application 105. A 3D application 105 may provide for one or more different frame rates during execution and may also include a setting for VSYNC in which the frame rate will be synced to the refresh rate of the display 160. The GPU 125 may also include a VSYNC controller component 130 operative to enforce the VSYNC setting to synchronize the FPS of a 3D application to the refresh rate of a display 160. The system 100 may also be communicatively coupled with the display 160. The display 160 may be associated with one or more refresh rates that control how often the display 160 refreshes its screen with a new frame. The system 100 may be able to lower the refresh rate of the display if there is a lower supportable setting available. Lowering the refresh rate of the display prior to forcing VSYNC may conserve even more battery power since the FPS required of the 3D application ay be even further reduced.

In the illustrated embodiment shown in FIG. 5, the CPU 110 may be executing a 3D application 105 at block 510. For example, one or more 3D applications 105 may be executing on the system 100 under the control of CPU 110. Each 3D application 105 may be associated with an instance of the graphics driver 120. Under normal operating conditions, the 3D application(s) will execute according to the settings specified within the given 3D application 105. The embodiments are not limited in this context.

The logic flow 500 may determine whether the system 100 is operating on battery power 140 at block 520. For example, the system 100 may be operative on battery power 140 or may receive power from an external DC source 150. An external DC source 150 may be representative of the system being plugged in to an alternating current (AC) outlet. The power from the AC outlet may pass through a rectifier that converts it to DC for operating the system 100. When the system 100 is receiving power from an external DC source 150, power consumption is less of an issue. However, when the system 100 is receiving power from a battery 140, power consumption is an issue because the charge in the battery 140 is limited and dwindles with system 100 use. The graphics driver 120 may be capable of determining when the system 100 is operating on battery power 140. In such cases, certain power savings techniques may be implemented to extend the life of the battery while powering the system 100. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 5, the logic flow 500 may determine a percentage level of remaining battery power 140 at block 530. For example, the graphics driver 120 may be operative to determine how much battery power 140 remains at a given time. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 5, the graphics driver 120 may determine whether the percentage level of remaining battery power 140 has dipped below a threshold at block 540. For example, the graphics driver 120 may be operative to determine how much battery power 140 remains at a given time and compare it to a threshold level. The system may be set to invoke power savings once the battery dips below a pre-defined threshold level rather than automatically conserve power upon detection of battery power 140. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 5, the logic flow 500 may determine whether the refresh rate for the display 160 can be reduced at block 550. For example, some displays may support multiple different refresh rates. The display 160 may be operating at a refresh rate of 75 Hz but may also be operable at a refresh rate of 60 Hz. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 5, the logic flow 500 may reduce the refresh rate of the display 160 at block 560. For example, if the display supports a lower refresh rate the system 100 may be able to instruct the display 160 to operate at a lower refresh rate than that which it is currently operating. In the example above, the refresh rate for the display may be reduced from 75 Hz to 60 Hz. The embodiments are not limited in this context.

In the illustrated embodiment shown in FIG. 5, the graphics driver 120 may force execution of the VSYNC setting when the system 100 is operating on battery power 140 below a threshold level at block 570. For example, an instance of the graphics driver 120 may be associated with a 3D application 105. The graphics driver 120 may have determined that the system 100 is operating on battery power 140 and that the battery power has dipped below a pre-defined threshold level. In an effort to conserve power while operating on battery power 140, the graphics driver 120 instance for a given 3D application 105 may enable or force VSYNC between the 3D application 105 and the display 160. The graphics driver 120 signals the GPU 125 to lower the frame rate to match the refresh rate of the display 160. The embodiments are not limited in this context.

The GPU 125 may present frames to the display 160 at block 580. For example, the GPU 125 generates frames of video content for the display 160. If the system 100 is operating on battery power 140 below a threshold level, the GPU 125 may present the frames to the display 160 under VSYNC. The FPS for the 3D application 105 will be forced into VSYNC to match the refresh rate of the display 160. Consider a 3D application 105 operating with a frame rate of 90 FPS. The display 160 may have a refresh rate of 75 Hz. The refresh rate may have been reduced to 60 Hz at block 560 above. In this example, VSYNC will cap the GPU 125 workload at 60 FPS rather than 90. Since the GPU 125 does not have to generate the additional 30 frames its workload has been even further reduced thereby conserving power and further extending the life of the battery 140. The embodiments are not limited in this context.

The GPU 125 may present frames to the display 160 at block 590. For example, the GPU 125 generates frames of video content for the display 160. If the system 100 is operating on power form a external DC source 150 that is not the battery 140 or if the system 100 is operating on battery power 140 but above a threshold level, the GPU 125 may present the frames to the display 160 as intended by the 3D application 105. In this case, the FPS may be set to 90 by the 3D application 105. The embodiments are not limited in this context.

Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

FIG. 6 illustrates an embodiment of a system 600 that may be suitable for implementing the forced VSYNC processing embodiments of the disclosure. In embodiments, system 600 may be a system capable of forcing VSYNC although system 600 is not limited to this context. For example, system 600 may be incorporated into a personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and so forth.

In embodiments, system 600 comprises a platform 602 coupled to a display 620. Platform 602 may receive content from a content device such as content services device(s) 630 or content delivery device(s) 640 or other similar content sources. A navigation controller 650 comprising one or more navigation features may be used to interact with, for example, platform 602 and/or display 620. Each of these components is described in more detail below.

In embodiments, platform 602 may comprise any combination of a chipset 605, processor(s) 610, memory 612, storage 614, graphics subsystem 615, applications 616 and/or radio 618. Chipset 605 may provide intercommunication among processor 610, memory 612, storage 614, graphics subsystem 615, applications 616 and/or radio 618. For example, chipset 605 may include a storage adapter (not depicted) capable of providing intercommunication with storage 614.

Processor(s) 610 may be implemented as Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors, x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In embodiments, processor(s) 610 may comprise dual-core processor(s), dual-core mobile processor(s), and so forth.

Memory 612 may be implemented as a volatile memory device such as, but not limited to, a Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), or Static RAM (SRAM).

Storage 614 may be implemented as a non-volatile storage device such as, but not limited to, a magnetic disk drive, optical disk drive, tape drive, an internal storage device, an attached storage device, flash memory, battery backed-up SDRAM (synchronous DRAM), and/or a network accessible storage device. In embodiments, storage 614 may comprise technology to increase the storage performance enhanced protection for valuable digital media when multiple hard drives are included, for example.

Graphics subsystem 615 may perform processing of images such as still or video for display. Graphics subsystem 615 may be a graphics processing unit (GPU) or a visual processing unit (VPU), for example. An analog or digital interface may be used to communicatively couple graphics subsystem 615 and display 620. For example, the interface may be any of a High-Definition Multimedia Interface, DisplayPort, wireless HDMI, and/or wireless HD compliant techniques. Graphics subsystem 615 could be integrated into processor 610 or chipset 605. Graphics subsystem 615 could be a stand-alone card communicatively coupled to chipset 605.

The graphics and/or video processing techniques described herein may be implemented in various hardware architectures. For example, graphics and/or video functionality may be integrated within a chipset. Alternatively, a discrete graphics and/or video processor may be used. As still another embodiment, the graphics and/or video functions may be implemented by a general purpose processor, including a multi-core processor. In a further embodiment, the functions may be implemented in a consumer electronics device.

Radio 618 may include one or more radios capable of transmitting and receiving signals using various suitable wireless communications techniques. Such techniques may involve communications across one or more wireless networks. Exemplary wireless networks include (but are not limited to) wireless local area networks (WLANs), wireless personal area networks (WPANs), wireless metropolitan area network (WMANs), cellular networks, and satellite networks. In communicating across such networks, radio 618 may operate in accordance with one or more applicable standards in any version.

In embodiments, display 620 may comprise any television type monitor or display. Display 620 may comprise, for example, a computer display screen, touch screen display, video monitor, television-like device, and/or a television. Display 620 may be digital and/or analog. In embodiments, display 620 may be a holographic display. Also, display 620 may be a transparent surface that may receive a visual projection. Such projections may convey various forms of information, images, and/or objects. For example, such projections may be a visual overlay for a mobile augmented reality (MAR) application. Under the control of one or more software applications 616, platform 602 may display user interface 622 on display 620.

In embodiments, content services device(s) 630 may be hosted by any national, international and/or independent service and thus accessible to platform 602 via the Internet, for example. Content services device(s) 630 may be coupled to platform 602 and/or to display 620. Platform 602 and/or content services device(s) 630 may be coupled to a network 660 to communicate (e.g., send and/or receive) media information to and from network 660. Content delivery device(s) 640 also may be coupled to platform 602 and/or to display 620.

In embodiments, content services device(s) 630 may comprise a cable television box, personal computer, network, telephone, Internet enabled devices or appliance capable of delivering digital information and/or content, and any other similar device capable of unidirectionally or bidirectionally communicating content between content providers and platform 602 and/display 620, via network 660 or directly. It will be appreciated that the content may be communicated unidirectionally and/or bidirectionally to and from any one of the components in system 600 and a content provider via network 660. Examples of content may include any media information including, for example, video, music, medical and gaming information, and so forth.

Content services device(s) 630 receives content such as cable television programming including media information, digital information, and/or other content. Examples of content providers may include any cable or satellite television or radio or Internet content providers. The provided examples are not meant to limit embodiments of the invention.

In embodiments, platform 602 may receive control signals from navigation controller 650 having one or more navigation features. The navigation features of controller 650 may be used to interact with user interface 622, for example. In embodiments, navigation controller 650 may be a pointing device that may be a computer hardware component (specifically human interface device) that allows a user to input spatial (e.g., continuous and multi-dimensional) data into a computer. Many systems such as graphical user interfaces (GUI), and televisions and monitors allow the user to control and provide data to the computer or television using physical gestures.

Movements of the navigation features of controller 650 may be echoed on a display (e.g., display 620) by movements of a pointer, cursor, focus ring, or other visual indicators displayed on the display. For example, under the control of software applications 616, the navigation features located on navigation controller 650 may be mapped to virtual navigation features displayed on user interface 622, for example. In embodiments, controller 650 may not be a separate component but integrated into platform 602 and/or display 620. Embodiments, however, are not limited to the elements or in the context shown or described herein.

In embodiments, drivers (not shown) may comprise technology to enable users to instantly turn on and off platform 602 like a television with the touch of a button after initial boot-up, when enabled, for example. Program logic may allow platform 602 to stream content to media adaptors or other content services device(s) 630 or content delivery device(s) 640 when the platform is turned “off.” In addition, chip set 605 may comprise hardware and/or software support for 5.1 surround sound audio and/or high definition 6.1 surround sound audio, for example. Drivers may include a graphics driver for integrated graphics platforms. In embodiments, the graphics driver may comprise a peripheral component interconnect (PCI) Express graphics card.

In various embodiments, any one or more of the components shown in system 600 may be integrated. For example, platform 602 and content services device(s) 630 may be integrated, or platform 602 and content delivery device(s) 640 may be integrated, or platform 602, content services device(s) 630, and content delivery device(s) 640 may be integrated, for example. In various embodiments, platform 602 and display 620 may be an integrated unit. Display 620 and content service device(s) 630 may be integrated, or display 620 and content delivery device(s) 640 may be integrated, for example. These examples are not meant to limit the invention.

In various embodiments, system 600 may be implemented as a wireless system, a wired system, or a combination of both. When implemented as a wireless system, system 600 may include components and interfaces suitable for communicating over a wireless shared media, such as one or more antennas, transmitters, receivers, transceivers, amplifiers, filters, control logic, and so forth. An example of wireless shared media may include portions of a wireless spectrum, such as the RF spectrum and so forth. When implemented as a wired system, system 600 may include components and interfaces suitable for communicating over wired communications media, such as input/output (I/O) adapters, physical connectors to connect the I/O adapter with a corresponding wired communications medium, a network interface card (NIC), disc controller, video controller, audio controller, and so forth. Examples of wired communications media may include a wire, cable, metal leads, printed circuit board (PCB), backplane, switch fabric, semiconductor material, twisted-pair wire, co-axial cable, fiber optics, and so forth.

Platform 602 may establish one or more logical or physical channels to communicate information. The information may include media information and control information. Media information may refer to any data representing content meant for a user. Examples of content may include, for example, data from a voice conversation, videoconference, streaming video, electronic mail (“email”) message, voice mail message, alphanumeric symbols, graphics, image, video, text and so forth. Data from a voice conversation may be, for example, speech information, silence periods, background noise, comfort noise, tones and so forth. Control information may refer to any data representing commands, instructions or control words meant for an automated system. For example, control information may be used to route media information through a system, or instruct a node to process the media information in a predetermined manner. The embodiments, however, are not limited to the elements or in the context shown or described in FIG. 6.

As described above, system 600 may be embodied in varying physical styles or form factors. FIG. 7 illustrates embodiments of a small form factor device 700 in which system 600 may be embodied. In embodiments, for example, device 700 may be implemented as a mobile computing device having wireless capabilities. A mobile computing device may refer to any device having a processing system and a mobile power source or supply, such as one or more batteries, for example.

As described above, examples of a mobile computing device may include a personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and so forth.

Examples of a mobile computing device also may include computers that are arranged to be worn by a person, such as a wrist computer, finger computer, ring computer, eyeglass computer, belt-clip computer, arm-band computer, shoe computers, clothing computers, and other wearable computers. In embodiments, for example, a mobile computing device may be implemented as a smart phone capable of executing computer applications, as well as voice communications and/or data communications. Although some embodiments may be described with a mobile computing device implemented as a smart phone by way of example, it may be appreciated that other embodiments may be implemented using other wireless mobile computing devices as well. The embodiments are not limited in this context.

As shown in FIG. 7, device 700 may comprise a housing 702, a display 704, an input/output (I/O) device 706, and an antenna 708. Device 700 also may comprise navigation features 712. Display 704 may comprise any suitable display unit for displaying information appropriate for a mobile computing device. I/O device 706 may comprise any suitable I/O device for entering information into a mobile computing device. Examples for I/O device 706 may include an alphanumeric keyboard, a numeric keypad, a touch pad, input keys, buttons, switches, rocker switches, microphones, speakers, voice recognition device and software, and so forth. Information also may be entered into device 700 by way of microphone. Such information may be digitized by a voice recognition device. The embodiments are not limited in this context.

Various embodiments may be implemented using hardware elements, software elements, or a combination of both. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor.

Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Further, some embodiments may be described using the expression “coupled” and “connected” along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some embodiments may be described using the terms “connected” and/or “coupled” to indicate that two or more elements are in direct physical or electrical contact with each other. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

It is emphasized that the Abstract of the Disclosure is provided to allow a reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein,” respectively. Moreover, the terms “first,” “second,” “third,” and so forth, are used merely as labels, and are not intended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and/or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. 

What is claimed is:
 1. An apparatus comprising: a processor circuit; and a graphics driver operative on the processor circuit to execute an application having a three dimensional (3D) workload, the graphics driver operative to enable a vertical synchronization (VSYNC) setting while the processor circuit is operating on battery power, the VSYNC setting to enable VSYNC operations to synchronize a frames per second (FPS) specified by the application with a refresh rate for a display.
 2. The apparatus of claim 1, the graphics driver operative to determine when the processor circuit is operating on battery power.
 3. The apparatus of claim 2, the graphics driver operative to determine a threshold percentage level of remaining battery power.
 4. The apparatus of claim 3, the graphics driver operative to enable the vertical synchronization (VSYNC) operation when the percentage level of remaining battery power is lower than the threshold percentage level.
 5. The apparatus of claim 4, the graphics driver operative to override a VSYNC setting within the application to enable vertical synchronization (VSYNC) operations when the percentage level of remaining battery power is lower than the threshold percentage level.
 6. The apparatus of claim 1, the graphics driver operative to override a VSYNC setting within the application to enable vertical synchronization (VSYNC) operations while the processor circuit is operating on battery power.
 7. The apparatus of claim 1, the graphics driver operative to return VSYNC control to the application when the processor circuit is not operating on battery power.
 8. The apparatus of claim 1 comprising a battery operative to power the processor circuit.
 9. The apparatus of claim 1, the graphics driver operative to lower the refresh rate of the display prior to enabling the VSYNC setting.
 10. The apparatus of claim 1 comprising a second processor circuit communicatively coupled to the processor circuit, the second processor circuit operative to present frames for rendering on the display.
 11. The apparatus of claim 10, the processor circuit comprising a central processing unit (CPU), the second processor circuit comprising a graphics processing unit (GPU), and further comprising a display communicatively coupled with the GPU.
 12. A method, comprising: executing an application having a 3D workload on a central processing unit (CPU); enabling a vertical synchronization (VSYNC) setting when the CPU is operating on battery power, the VSYNC setting enabling VSYNC operations to synchronize a frames per second (FPS) specified by the application with a refresh rate for a display; executing VSYNC operations on a graphics processing unit (GPU); and presenting frames for rendering to the display.
 13. The method of claim 12, comprising: determining a percentage level of remaining battery power while the CPU is operating on battery power.
 14. The method of claim 13, comprising: enabling the vertical synchronization (VSYNC) operations when the percentage level of remaining battery power dips beneath a threshold percentage level.
 15. The method of claim 13, comprising: overriding a VSYNC setting within the application to enable the vertical synchronization (VSYNC) operations when the percentage level of remaining battery power is lower than a threshold percentage level.
 16. The method of claim 12, comprising: overriding a VSYNC setting within the application to enable the vertical synchronization (VSYNC) operations when the CPU is operating on battery power.
 17. The method of claim 12, comprising: lowering the refresh rate of the display prior to executing the VSYNC operations.
 18. The method of claim 12, comprising: returning VSYNC control to the application when the CPU is not operating on battery power.
 19. An article of manufacture comprising a computer-readable storage medium containing instructions that when executed cause a system to: execute an application having a 3D workload on a central processing unit (CPU); enable a vertical synchronization (VSYNC) function while the CPU is operating on battery power, the VSYNC function operative to synchronize a frames per second (FPS) specified by the application with a refresh rate for a display; execute the VSYNC function on a graphics processing unit (GPU); and present frames for rendering to the display.
 20. The article of claim 19 containing instructions that when executed cause a system to: determine a percentage level of remaining battery power while the CPU is operating on battery power.
 21. The article of claim 20 containing instructions that when executed cause a system to: enable the vertical synchronization (VSYNC) function when the percentage level of remaining battery power dips beneath a threshold percentage level.
 22. The article of claim 20 containing instructions that when executed cause a system to: override a VSYNC setting within the application to enable the vertical synchronization (VSYNC) function when the percentage level of remaining battery power dips beneath a threshold percentage level.
 23. The article of claim 19 containing instructions that when executed cause a system to: override a VSYNC setting within the application to enable the vertical synchronization (VSYNC) function while the system is operating on battery power.
 24. The article of claim 19 containing instructions that when executed cause a system to: lower the refresh rate of the display prior to executing the VSYNC function.
 25. The article of claim 19 containing instructions that when executed cause a system to: return VSYNC control to the application when the system is not operating on battery power. 